A vignette for the traffic safety review paper
This vignette serves as the supplementary materials to create reproducible examples provided in a detailed review on transportation safety research by Qiong et al.
Qiong Hu, Amir Mehdizadeh, Nasrin Mohabbati Kalejahi, Mohammad Ali Alamdar Yazdi, Miao Cai,Aleksandr Vinel, Steven E. Rigdon, Karen C. Davis, Fadel M. Megahe. Bridging the Gap between Transportation Safety Research and its Incorporation inOptimization Models: a Detailed Review and Perspective. Submitted to Transportation Research Part C: Emerging Technologies.
The vignette includes example on four aspects:
- Bibliographic analysis
- Extracting online transportation safety data
- Descriptive analytic tools
1 Bibliographic analysis
2 Extracting online transportation safety data
2.2 Traffic flow data
2.2.1 Historical data (yearly)
FHWA has provided Annual Average Daily Traffic (AADT) from 2011 to 2017. As an illustration, the following code chunk displays the first five observations of AADT data for Missouri 2017.
# Using Missouri as an example
fhwai = foreign::read.dbf("data/missouri2017/Missouri2017.dbf")
datatable(
head(fhwai),
caption = 'Historical traffic data in Missouri, 2017',
class = 'cell-border stripe',
extensions = c('Buttons', 'ColReorder'),
options = list(
dom = 'Bfrtip', colReorder = TRUE, scrollX = TRUE,
buttons = c('copy', 'csv', 'excel', 'pdf', 'print')
))The downloaded “shape files” can be converted to different data formats (e.g., .csv) using the following R code.
2.2.2 Real-time data (<= 5 minutes)
There are several sources for getting real-time traffic data. Some of the states in the USA are equipped with loop detectors and video cameras. Departments of Transportation (DoT) can provide this data. Further, HERE website also provides near real-time traffic data with the limitation of x APIs per day for free. Later, a detailed instruction for getting this data form HERE website is provided.
- State DoTs|loop detector
- State DoTs|video frames
HERE Website
2.3 Weather data
2.3.1 Historical (daily)
2.3.2 Real-time (<= 1 hour)
In this part, we show how to get both historical and real-time weather data using DarkSky API. It can be used in both Python and R. Before using the DarkSky API to get weather data, you need to register for a API key on its official website. The first 1000 API requests you make each day are free, but each API request over the 1000 daily limit will cost you $0.0001, which means a million extra API requests will cost you 100 USD.
To get weather data from the DarkSky API, you need to provide the following information on trucks:
- latitude
- longitude
- date and time
Then you can pass these three parameters to the get_forecast_for() function in darksky package in R.
source("private/DarkSkyAPIkey.R")
Sys.setenv(DARKSKY_API_KEY = myDarkSkyAPIkey) # you need to use your own "myDarkSkyAPIkey"
dat = structure(list(
latitude = c(41.3473127, 41.8189037, 32.8258477, 40.6776808, 40.2366043),
longitude = c(-74.2850908, -73.0835104, -97.0306677, -75.1450753, -76.9367494),
time = structure(c(1453101738, 1437508088, 1436195038, 1435243088, 1454270680),
class = c("POSIXct", "POSIXt"), tzone = "UTC")),
row.names = c(NA, -5L), class = "data.frame"
)
weather_dat <- pmap(
list(dat$latitude, dat$longitude, dat$time),
get_forecast_for)2.3.2.1 DarkSky returned data
For each observation (a combination of latitude, longitude, date and time), the darksky API returns a list of 3 data.frames:
- hourly weather. 24 hourly observations for each 15 weather variables in that day.
- daily weathe. 1 observations for each 34 weather variables in that day.
- current weather. 1 observations for each 15 weather variables at the assigned time point.
The variables include: apparent (feels-like) temperature, atmospheric pressure, dew point, humidity, liquid precipitation rate, moon phase, nearest storm distance, nearest storm direction, ozone, precipitation type, snowfall, sun rise/set, temperature, text summaries, uv index, wind gust, wind speed, wind direction
hourly weather
datatable(
head(weather_dat[[1]]$hourly),
caption = 'Hourly weather provided by the DarkSky API',
class = 'cell-border stripe',
extensions = c('Buttons', 'ColReorder'),
options = list(
dom = 'Bfrtip', colReorder = TRUE, scrollX = TRUE,
buttons = c('copy', 'csv', 'excel', 'pdf', 'print')
))%>%
formatStyle( 0, target= 'row', lineHeight='80%')daily weather
datatable(
head(weather_dat[[1]]$daily),
caption = 'Daily weather provided by the DarkSky API',
class = 'cell-border stripe',
extensions = c('Buttons', 'ColReorder'),
options = list(
dom = 'Bfrtip', colReorder = TRUE, scrollX = TRUE,
buttons = c('copy', 'csv', 'excel', 'pdf', 'print')
))%>%
formatStyle( 0, target= 'row', lineHeight='80%')currently weather
datatable(
head(weather_dat[[1]]$currently),
caption = 'Current weather provided by the DarkSky API',
class = 'cell-border stripe',
extensions = c('Buttons', 'ColReorder'),
options = list(
dom = 'Bfrtip', colReorder = TRUE, scrollX = TRUE,
buttons = c('copy', 'csv', 'excel', 'pdf', 'print')
))%>%
formatStyle( 0, target= 'row', lineHeight='80%')3 Descriptive analytic tools
3.1 An example of clustering
The following codes attempts to replicate the visual clustering approach from
Van Wijk, Jarke J., and Edward R. Van Selow. 1999. “Cluster and Calendar Based Visualization of Time Series Data.” In Information Visualization, 1999.(Info Vis’ 99) Proceedings. 1999 IEEE Symposium on, 4-9. IEEE.
A brief example of applying EDA methods on traffic data is provided here. The goal of this example is to illustrate the efficiency of the mentioned tools in the transportation context. There is no predetermined way to utilize these methods. The efficiency of each method highly depends on the nature of the problem. Hence, the challenge is to choose the right tool which fits the best.
3.1.1 Collecting Data
Hourly vehicle counts data is used in this example. It provides the number of vehicles which passed along a particular segment of a road in one hour. Data is extracted from the Georgia Department of Transportation (GDoT) (Georgia Department of Transportation, 2015) for 2015 from station 121-5505 which located in Atlanta. GDoT provides data in separate sheets for each month. After extracting and cleaning data, it was combined to one sheet with 365 rows (days) and 24 columns (hours). Data can be downloaded from GDoT.
3.1.2 Clustering
It is almost impossible to understand raw data and also discover interesting patterns in it by just looking at 8760 (370 * 24) data cells. Hence, K-means clustering method is utilized here to present data in a more understandable format. K-means clustering is a common technique to explore data and discover patterns by grouping similar data to predefined (k) number of clusters. K-means clustering aims to group data into k clusters in a way to minimize the within-cluster sum of squares (WCSS). To find the optimal number of clusters, we have used a method that was suggested by Pham et al. (2005). According to the following graph two is the best number of clusters to group this data.
trafficflow.df <- readr::read_csv("data/georgia-TFdata-station-121-5505-Yr2015.csv")
trafficflow.df$Date <- as.Date(trafficflow.df$Date, format='%d-%b')
opt = Optimal_Clusters_KMeans(
as.data.frame(trafficflow.df[,4:27]), max_clusters = 10,
plot_clusters = T, criterion = 'distortion_fK', fK_threshold = 0.85,
initializer = 'optimal_init', tol_optimal_init = 0.2,
max_iters = 10000)num_clusters <- which.min(opt) # Based on the results, we should use k=2 clusters in kmeans
km = KMeans_arma(
as.data.frame(trafficflow.df[,4:27]), clusters = num_clusters,
n_iter = 10000, seed_mode = "random_subset", verbose = F, CENTROIDS = NULL)
pr = predict_KMeans(data.frame(trafficflow.df[,4:27]), km)
trafficflow.df$cluster.num <- as.vector(pr) %>% as.factor()
table(trafficflow.df$cluster.num)##
## 1 2
## 119 246
3.1.3 Visualization
Now, k-means clustering can be applied. The output of this step is a column which its value is either one or two,indicating that each row of data (day) belongs to cluster one or two. Now data is divided into two groups. However, still we need to transfer data to a visual format to somehow validate and guide the clustering process. Since our data contains temporal information, we have used Cluster Calendar View visualization technique which is introduced by Van Wijk and Van Selow (1999). In this technique, a calendar represents the temporal information of data and by using color coding, differences between clusters are distinguished. The following graph shows a cluster calendar view for our data. It clearly has found meaningful patterns in the vehicle counts data. Weekends and weekdays have different traffic patterns. Besides, it has captured some of the holidays. For example, the 4th of July (Independence Day) which is a weekday, is colored by light blue. It means that this day has a similar traffic pattern with weekends. In addition, the clustering method has identified other holidays like Martin Luther King Day, Memorial Day, Labor Day, Thanksgiving Day and Christmas Day.
col.brewer.pal <- brewer.pal(11, "Paired")
p2 <- ggcal(trafficflow.df$Date,trafficflow.df$cluster.num) +
theme(legend.position="top") +
scale_fill_manual(values = c("1"=col.brewer.pal[1], "2"=col.brewer.pal[2]))
p2Furthermore, a line chart (following graph) is used to show the average hourly traffic data for the two clusters. Results show that each cluster has different peaks and valleys. On the weekdays, 7 AM and 4 PM have the greatest number of vehicles which can be explained by the official working hours. On the other hand, on weekends, the traffic peak is around 1 PM which maybe refers to some people going out for lunch.
summary.df <- group_by(trafficflow.df,cluster.num)
summary.df <- summarise_all(summary.df,funs(mean))
plot.df <- subset(summary.df, select = -c(2:4))
plot.df <- melt(plot.df, value.name="Traffic.Flow",
variable.name="Hour",id.vars="cluster.num")
plot.df$cluster.num <- as.factor(plot.df$cluster.num)
p1 <- plot.df %>%
ggplot(aes(x = Hour, y = Traffic.Flow, group=cluster.num, color=cluster.num)) +
geom_line(size=2) + theme_bw() +
theme(legend.position="top", axis.text.x=element_text(angle=90, hjust=1)) +
scale_color_brewer("Paired")
p1To sum up, it seems that K-means clustering method was very efficient here. We applied raw data as inputs to this method and as outputs we could discover patterns (weekdays and weekends traffic patterns) and also with the help of visualization technique we obtained a considerable information about the data.
4 Data visualization
5 Statistical models
References
Department of Epidemiology and Biostatistics, Saint Louis University. Email address miao.cai@slu.edu↩
Department of Industrial and Systems Engineering, Auburn University. Email address azm0127@auburn.edu↩
Carey Business School, Johns Hopkins Universitymza0052@auburn.edu↩
Farmer School of Business, Miami University. Email address fmegahed@miamioh.edu.↩